The Main Injector Beam Position Monitor Front-End Software

The front-end software developed for the Main Injector (MI) BPM upgrade is described. The software is responsible for controlling a VME crate, equipped with a Motorola PowerPC board running the VxWorks operating system, a custom made timing board and up to 10 commercial digitizer boards. The complete MI BPM system is composed of 7 independent units, each collecting data from 19 to 38 BPM pickups. The MI BPM system uses several components already employed on the successful upgrade of another Fermilab machine, the Tevatron. The front-end software framework developed for the Tevatron BPM upgrade is the base for building the MI front-end software. The framework is implemented in C++ as a generic component library (GBPM) that provides an event-driven data acquisition environment. Functionality of GBPM is extended to meet MI BPM requirements, such as the ability to handle and manage data from multiple cycles; perform readout of the digitizer boards without disrupting or missing subsequent cycles; transition between closed orbit and turn-by-turn modes within a cycle, using different filter and timing configurations; and allow the definition of new cycles during normal operation

Status Report of the DPHEP Study Group: Towards a Global Effort for Sustainable Data Preservation in High Energy Physics

Data from high-energy physics (HEP) experiments are collected with significant financial and human effort and are mostly unique. An inter-experimental study group on HEP data preservation and long-term analysis was convened as a panel of the International Committee for Future Accelerators (ICFA). The group was formed by large collider-based experiments and investigated the technical and organisational aspects of HEP data preservation. An intermediate report was released in November 2009 addressing the general issues of data preservation in HEP. This paper includes and extends the intermediate report. It provides an analysis of the research case for data preservation and a detailed description of the various projects at experiment, laboratory and international levels. In addition, the paper provides a concrete proposal for an international organisation in charge of the data management and policies in high-energy physics

A Roadmap for HEP Software and Computing R&D for the 2020s

Particle physics has an ambitious and broad experimental programme for the coming decades. This programme requires large investments in detector hardware, either to build new facilities and experiments, or to upgrade existing ones. Similarly, it requires commensurate investment in the R&D of software to acquire, manage, process, and analyse the shear amounts of data to be recorded. In planning for the HL-LHC in particular, it is critical that all of the collaborating stakeholders agree on the software goals and priorities, and that the efforts complement each other. In this spirit, this white paper describes the R&D activities required to prepare for this software upgrade.Peer reviewe

The Main Injector Beam Position Monitor Front-End Software

Abstract. The front-end software developed for the Main Injector (MI) BPM upgrade is described. The software is responsible for controlling a VME crate equipped with a Motorola PowerPC board running the VxWorks operating system, a custom-made timing board, and up to 10 commercial digitizer boards. The complete MI BPM system is composed of 7 independent units, each collecting data from 19 to 38 BPM pickups. The MI BPM system uses several components already employed on the successful upgrade of another Fermilab machine, the Tevatron. The front-end software framework developed for the Tevatron BPM upgrade is the base for building the MI front-end software. The framework is implemented in C++ as a generic component library (GBPM) that provides an event-driven data acquisition environment. Functionality of GBPM is extended to meet MI BPM requirements, such as the ability to handle and manage data from multiple cycles; perform readout of the digitizer boards without disrupting or missing subsequent cycles; transition between closed orbit and turn-by-turn modes within a cycle, using different filter and timing configurations; and allow the definition of new cycles during normal operation

The Main Injector Beam Position Monitor Front-End Software

Abstract. The front-end software developed for the Main Injector (MI) BPM upgrade is described. The software is responsible for controlling a VME crate, equipped with a Motorola PowerPC board running the VxWorks operating system, a custom made timing board and up to 10 commercial digitizer boards. The complete MI BPM system is composed of 7 independent units, each collecting data from 19 to 38 BPM pickups. The MI BPM system uses several components already employed on the successful upgrade of another Fermilab machine, the Tevatron. The front-end software framework developed for the Tevatron BPM upgrade is the base for building the MI front-end software. The framework is implemented in C++ as a generic component library (GBPM) that provides an event-driven data acquisition environment. Functionality of GBPM is extended to meet MI BPM requirements, such as the ability to handle and manage data from multiple cycles; perform readout of the digitizer boards without disrupting or missing subsequent cycles; transition between closed orbit and turn-by-turn modes within a cycle, using different filter and timing configurations; and allow the definition of new cycles during normal operation

FERRY: access control and quota management service

Fermilab developed the Frontier Experiments RegistRY (FERRY) service that provides a centralized repository for access control and job management attributes such as batch and storage access policies, quotas, batch priorities and NIS attributes for cluster configuration. This paper describes the FERRY architecture, deployment and integration with services that consume the stored information. The Grid community has developed several access control management services over the last decade. Over time, services for Fermilab experiments have required the collection and management of more access control and quota attributes. At the same time, various services used for this purpose, namely VOMS-Admin, GUMS and VULCAN, are being abandoned by the community. FERRY has multiple goals: maintaining a central repository for currently scattered information related to users' attributes, providing a Restful API that allows uniform data retrieval by services, and providing a replacement service for all the abandoned grid services. FERRY is integrated with the ServiceNow (SNOW) ticketing service and uses it as its user interface. In addition to the standard workflows for request approval and task creation, SNOW invokes orchestration that automates access to FERRY API. Our expectation is that FERRY will drastically improve user experience as well as decrease effort required by service administrators